What this PR does / why we need it:

This PR fixes an issue where the initial install flow preflight page would not be displayed if the application's preflight spec was included in a Secret or ConfigMap within the Helm chart templates.

Key Changes:

• Backend - We were not parsing preflights out of the rendered templates when populating the rendered kotsKinds directory for a given app version. We do this on-the-fly when we run preflights, which is why the checks would still run, but not having these saved as part of the kotsKinds in the archive meant that the preflight_spec field in the database would not be set, us returning hasPreflight: false back to the frontend.
• Frontend - The application details are now re-fetched after the configuration is saved successfully. This is necessary since the hasPreflight field may not be set until the configuration is saved and the version is rendered. This would be the case for a Helm chart that has required configuration, but no default values.

Which issue(s) this PR fixes:

https://app.shortcut.com/replicated/story/96941/preflight-page-not-displayed-in-kots-admin-console-install-flow-for-preflight-specs-in-helm-charts

Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Fixes an issue where the initial install flow preflight page would not be displayed if the application's preflight spec was included in a Secret or ConfigMap within the Helm chart templates

Does this PR require documentation?

NONE